Method and system for negotiation of media between communication devices for multiplexing multiple media types

ABSTRACT

A method of negotiation of media between a source communication device and a destination communication device for multiplexing multiple media types on an IP transport address comprises the source communication device generating an offer message comprising an extension to the ICE protocol according to RFC 5245 to specify the IP transport address whereon the multiple media types can he multiplexed, wherein the offer message comprising the extension indicates support for both the multiplexing and a non-multiplexing of the multiple media types, and sending the offer message from the source communication device to the destination communication device.

FIELD OF INVENTION

The invention relates a method of negotiation of media between a sourcecommunication device and a destination communication device formultiplexing multiple media types on an IP transport address. Theinvention further relates to a computer program product for executingsuch a method and to a source communication device for negotiating ofthe media between the source communication device and a destinationcommunication device.

BACKGROUND OF THE INVENTION

The Internet Protocol (IP) is a widely used protocol which nowadays isextensively used for telecommunication, for example for Voice over IP(VOIP). Along with voice data, it is possible to convey via IP otherdata such as a picture, e.g. in form of a bitmap, and/or text, e.g. inthe form of an ASCII file (American Standard Code for ComputerInformation Interchange). It is thus possible to establish a multimediasession using voice along with text and/or pictures/video data, e.g. inthe form of a video conference.

In order to reduce the number of flows of messages/data betweenparticipants for example in a conference to increase reliability andefficiency of the conference session, there is need to multiplexmultiple media (audio, video and/or other data such as text, tablesetc.) on to a single 5 Tuple (IP Address and Ports) with the result ofreducing the number of IP transports, i.e. IP addresses and/or IP ports,used during a multimedia session. Therefore, another positive effect ofthe multiplexing of multiple media is that the total number of used IPtransport addresses and/or ports is reduced per session leading to alarger number of multimedia sessions being able to be run simultaneouslyif the total number of IP transport addresses and/or ports is limited.

In telecommunications and computer networks, multiplexing, also known asmixing, is a method by, which digital data streams are combined into onesignal over a shared medium. The aim is to share an expensive resource.For example, in telecommunications, several telephone calls may becarried using one wire. Examples for Multiplexing methods include Timedivision Multiplexing (TDM) and Frequency division Multiplexing (FDM).The multiplexed signal is transmitted over a communication channel,which may be a physical transmission medium. The multiplexing dividesthe capacity of the high-level communication channel into severallow-level logical channels, one for each message signal or data streamto be transferred. A reverse process, known as demultiplexing, canextract the original channels on the receiver side.

A 5-Tuple is made up of source IP address, destination IP address,source port number, destination port number and the protocol in use andis one of the elements that need to be negotiated between two peersbefore communication can take place. The negotiation between asending/source entity and a receiving/destination entity of thesignalling and payload parameters based on the Internet Protocol needsto be performed in a manner that is both interoperable with existinglegacy devices which don't support this multiplexing and newimplementations that do. The aim here is to also try to limit the numberof SDP (Session Description Protocol) offer/answers exchanges needed toestablish media, i.e. a payload path whereon media are transmittedbetween the source entity and the destination entity, SDP is a formatfor describing streaming media initialization parameters. The IETF(Internet Engineering Task Force) published the original specificationas an IETF Proposed Standard in April 1998, and subsequently published arevised specification as an IETF Proposed Standard as RFC 4566 in July2006. SDP is intended for describing multimedia communication sessionsfor the purposes of session announcement, session invitation, andparameter negotiation. SDP does not deliver media itself but is used fornegotiation between end points/terminals/communication devices of mediatype, format, and all associated properties. The set of properties andparameters are often called a session profile.

Possible ways to reduce the number of flows of data/messages/streamsbetween conference participants for efficiency and reliability masonshave been discussed in the IETF, the current approaches being proposedare discussed in the following drafts submitted to the IETF:draft-ietf-mmusic-sdp-bundle-negotiation-03 anddraft-ejzak-mmusic-bundle-alternatives-01 which are incorporated hereinas an integral part of this application by reference. Both of theseapproaches describe a mechanism for multiplexing different media using anew SDP grouping mechanism called “BUNDLE”. In SDP, each media isdescribed by what is called an m-line which includes the source port tobe used for that media. The approaches describe how a mechanism forgrouping these m-lines would work and how the ports are negotiated usingthe existing m-line. The disadvantage of both of these approaches isthat they cannot fully specify the 5-tuple to be used for multiplexinguntil they have determined that the peer supports the bundling mechanismso these approaches are not sufficiently efficient.

SUMMARY OF THE INVENTION

The object of the invention is therefore to enable a source entity tonegotiate with a destination entity to fully specify a 5-tuple to beused for multiplexing in a multimedia session without determination thatthe destination entity supports a multiplexing/grouping mechanism. Inparticular, the source entity should be enabled to negotiate with adestination entity to fully specify a 5-tuple to be used formultiplexing in an IP multimedia session without determination that thedestination entity supports the SDP grouping mechanism called “BUNDLE”.This object is solved by the method of negotiation of media between asource communication device and a destination communication device formultiplexing multiple media types on an IP transport address, whereinthe method comprises the source communication device generating an offermessage comprising an extension to the ICE protocol according to RFC5245 to specify the IP transport address whereon the multiple mediatypes can be multiplexed, wherein the offer message comprising theextension indicates support for both the multiplexing and anon-multiplexing of the multiple media types, and sending the offermessage from the source communication device to the destinationcommunication device.

The source and/or destination communication device, respectively, may bean IP phone of a local area network, a wide area network, such as theInternet, or any other area network. This communication device may beany mobile or stationary entity capable of sending and/or receiving dataover a communication connection. Alternatively to the IP-phone, thecommunication device may be a mobile phone, a Personal DigitalAssistant, a tablet PC, a laptop or the like. The communication devicemay also be a stationary unit such as a desktop PC or a server.

ICE is a technique used in computer networking involving network addresstranslator's (NATs) in Internet applications of Voice over InternetProtocol (VoIP), peer-to-peer communications, video, instant messagingand other interactive media. In such applications, NAT traversal is animportant component to facilitate communications involving hosts onprivate network installations, often located behind firewalls. ICE isdeveloped by the Internet Engineering Task Force MMUSIC working groupand is published as RFC 5245.

The method may use the extension to the ICE (Interactive ConnectivityEstablishment) according to the standard (RFC 5245, RFC: Recall Forcomments in a form of a candidate to specify an IP transport address forthe candidate which can be used if the destination communication devicereceiving the candidate supports the extension and is able to multiplexmultiple media streams, e.g. audio, video, and/or other data, on to asingle transport address.

When used within an SDP Offer/Answer, wherein the SDP may be inaccordance with RFC 4566 and wherein the Offer/Answer may be accordingto RFC 3264, the source communication device generating the SDPOffer/Answer is enabled to generate SDP messages which, when received bya destination communication device that is not aware of this extension,appears as a conventional valid, i.e. normal, SDP Offer/Answer on whichthe destination communication device can respond to accordingly.

However when an SDP Offer is received by a destination communicationdevice, also called implementation, that is able to read, i.e. doesunderstand, this extension the destination communication device is ableto respond with an SDP Answer which specifies the multiplexed ports tobe used and is able to send media, i.e. payload, to the multiplex portspecified in the offer.

This means that within a single (RFC: 3264-)offer/answer cycle it ispossible to negotiate the (IP-)transport address to be used for mediawith legacy communication devices/implementations which are not aware ofthis extension and with implementations that are aware of the extension.

Communication devices/implementations which are aware of this extensionare now able to use the port specified in the extension rather than inthe ICE candidate port according to RFC 5245 and then follow existingICE procedures as specified in RFC 5245.

A possible name for the extension is “bundleport” but other names arepossible. Another ICE extension could be used to indicate which ICEcandidate(s) in an (SDP-)Offer may be multiplexed on to a singletransport.

An example offer message of the invention embodied in an SDP Offer in 21consecutive lines is shown in the following:

v=0

o=alice 2890844526 2890844526 IN IP4 host.sen.com

s=

c=IN IP4 192.0.2.2

t=0 0

a=group:BUNDLE foo bar

m=audio 10000 RTP/AVP 0 8 97

a=mid:foo

b=AS:200

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:97 iLBC/8000

a=candidate:1 1 UDP 1694498815 2001:::1 10000 typ host bundleport 10000

a=candidate:2 1 UDP 1694498814 192.0.2.2 20000 typ host bundleport 20000

m=video 10002 RTP/AVP 31 32

a=mid:bar

b=AS:1000

a=rtpmap:31 H261/90000

a=rtpmap:32 MPV/90000

a=candidate:1 1 UDP 1694498815 2001:::1 10002 typ host bundleport 10000

a=candidate:2 1 UDP 1694498814 192.0.2.2 20002 typ host bundleport 20000

In the inventive example, the offer contains he parts of the 5-tuplespecified by the offeror, i.e. source IP Address, Source Port and theProtocol. The other parts, i.e. Destination IP Address and Port wouldcome from the destination communication device/peer entity in the SDPanswer (not shown).

The prior art approaches discussed above describe how a mechanism forgrouping the m-lines would work and how the ports are negotiated usingthe existing m-line which are. The existing port is 10000 in line 7 and10002 in line 15. The inventive method builds on this grouping mechanismusing an extension the ICE protocol.

The ICE candidate explicitly specifies the port to be used formultiplexing media in line 13 for audio data: a=candidate:1 1 UDP1694498815 2001:::1 10000 typ host bundleport 10000. In the inventiveembodiment the source communication device is dual stack IPv4/6 andtherefore comprises both candidates in the offer in line 14 for theaudio data: a=candidate:2 1 UDP 1.694198814 192.0.2.2 20000 typ hostbundleport 20000. In the example the two candidates in line 13 and 14relate to the two transport addresses for Ipv4 and IPV6 independent of aused codec. The same 5-tuple is used whatever the codec may be.

For the video data, there are two ICE candidates comprised in the offermessage as well. The bundleport in line 20 indicates that the video canbe multiplexed with the audio on port 10000: a=candidate:1 1 UDP1694498815 2001:::1 10002 typ host bundleport 10000. If IPv6 instead ofIPv4 is used the bundle port will be port 20000: a=candidate:2 1 UDP1694498814 192.0.2.2. 20002 typ host bundleport 20000.

Lines 13, 14, 20 and 21 thus represent the inventive ICE extensions inthe embodiment shown above.

The disadvantage of the prior art approaches which are avoided byexecuting the inventive method is that these approaches cannot fullyspecify the 5-tuple to be used for multiplexing until they havedetermined that the destination communication device supports thebundling mechanism and are thus not sufficiently efficient. Theinventive method solves this problem in a downward compatible manner fora destination communication device/remote party supporting ICE.

In another embodiment the sending of the SDP offer message from thesource communication device to the destination communication device isexecuted before the source communication device receives informationabout a capability of the destination communication device to multiplexmultiple media types on an IP transport address.

If the offer message is received by the destination communication devicethat understands the extension, the destination communication device maybe enabled to respond to the source communication device with an answermessage which specifies at least on:e multiplexed port to be used forthe multiplexing, and, if the offer message is received by thedestination communication device that is unaware of the extension, theoffer message may be a valid offer message to the destinationcommunication device such that the destination communication device isenabled to respond to the offer message with sending a valid responsemessage to the source communication device.

The extension to the ICE protocol is advantageously used for initiatingthe “BUNDLE” SDP grouping mechanism for multiplexing different mediatypes.

Support for both the multiplexing and a non-multiplexing of the multiplemedia types is indicated, with advantage to the destinationcommunication device in a single message.

The extension may comprise in another embodiment at least one candidatespecifying an IP port to he used by the destination communication devicefor the multiplexing.

Further, the multiple media types may be multiplexed on a single IPtransport address and an IP port.

The offer message is formed in an embodiment of the invention as a SDPoffer message.

Here, the media for multiplexing multiple media types on an IP transportaddress may be negotiated between the source communication device andthe destination communication device in a single SOP offer/answer cycle.

With advantage, the destination communication device may respond validlywith sending a single message to the source communication deviceindependently of whether the destination communication device supportsthe multiplexing of multiple media types on an IP transport address ornot.

The source communication device and the destination communication devicemay be configured as peer-to-peer devices. The peer-to-peer devices maybe set up in an ad-hoc network for spontaneous negotiation of mediatypes.

A computer program product for executing the inventive method asoutlined above may be provided. The computer program product may be asoftware product comprising instructions. The computer program productmay be comprised by a machine readable medium wherein the machinereadable medium may be a floppy disk, a CD (Compact Disc), a DVD(Digital Versatile Disc), or any other suitable digital or analoguemedium.

The invention further comprises a source communication device fornegotiating of media between the source communication device and adestination communication device for multiplexing multiple media typeson an IP transport address, wherein the source communication devicecomprises an offer message generating unit configured to generate anoffer message comprising an extension to the ICE protocol according toRFC 5245 to specify the IP transport address whereon the multiple mediatypes can he multiplexed, wherein the offer message comprising theextension indicates support for both the multiplexing and anon-multiplexing of the multiple media types, and a sending unitconfigured to send the offer message from the source communicationdevice to the destination communication device.

The object of the invention is solved by this source communicationdevice for the same reasons as outlined above with respect to theinventive method. The source communication device may be a mobile phone,a wired phone, such as an office phone, a PDA (Personal DigitalAssistant), a PC (Personal Computer), a tablet PC or any othercommunication device comprising the apparatus features as outlinedabove. Respective forms as for the source communication device arepossible for the destination communication device.

The source communication device which may be a multimedia devicesupports ICE [RFC 5245], initiates communication with the destinationcommunication device which may be a peer device and supports the abilityto multiplex multiple media types on a single IP address and port. Thesource communication device may not know the capabilities of thedestination communication device and is able to indicate support forboth the multiplexing of media types and the non multiplex in a singlemessage to the destination communication device. The destinationcommunication device may respond with a single message independently ofwhether it supports the multiplex or not.

In a further embodiment, a communication system comprises the inventivesource communication device and a destination communication deviceconfigured to negotiate media with the source communication device.

Further embodiments and advantages of the invention are highlighted inthe following with respect to figures. For an improved clearness, thefigures are not true to scale or proportionate. In the figures, as longas not mentioned otherwise, same references indicate same parts withsame meaning.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic arrangement according to the invention, wherein asource communication device 1 is sending an offer message to adestination communication device 4 via a server 2 and gateway 3.

FIG. 2a is a schematic flow chart according to the invention between theentities shown in FIG. 1, wherein the destination communication devicesupports the ICE extension, and

FIG. 2b is another schematic flow chart according to the inventionbetween the entities shown in FIG. 1, wherein the destinationcommunication device does not support the ICE extension.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

In FIG. 1, the source communication device represented by a calling UserAgent 1, initiates the communication towards the destinationcommunication device represented by the called user agent 4. The sourcecommunication device does not know whether the called user agent 4supports multiplexing of media streams and provides its mediacapabilities and transport address to the calling user agent 1.

A signalling server 2 passes the communication establishment requests ofthe calling user agent 1 towards the intended recipient, the called useragent 4, via the gateway 3. The media gateway 3 may be optionallydeployed on the path between the source communication device and thedestination communication device which will relay both the signallingand payload messages between the devices, in short signalling and media.

The called user agent 4 using the destination communication devicereceives the offer message from the source communication device of thecalling user agent 1 to communicate with and respond to the calling useragent 1 with its own media capabilities and transport address.

In FIG. 2 a, the messages exchanged between the calling user agent 1,the server 2, the gateway 3, and the called user agent 4 are shown inthe case where the destination communication device of the called useragent 4 supports the ICE extension as comprised by the inventive SDPOffer (21 lines) discussed above. As the destination communicationdevice of the called user agent 4 supports the ICE extension of lines13, 14, 20, 21, it sets up a signaling path “SDP, ICECandidate+bundleport. Following the establishment of the signaling path,a payload path “Media” multiplexed an the same 5-Tuple for the audiodata as for the video data mentioned in the inventive SDP offer messageis used be the source communication device of the calling user agent 1and the destination communication device of the called user agent 4.

In FIG. 2b , the messages exchanged between the calling user agent 1,the server 2, the gateway 3, and the called user agent 4 are shown inthe case where the destination communication device of the called useragent 4 does not support the ICE extension as comprised by the inventiveSDP Offer (21 lines) discussed above. As the destination communicationdevice of the called user agent 4 does not support the ICE extension oflines 13, 14, 20, 21, it sets up separate payload paths using differentports for the audio data and the video data. Since in both cases, thedestination communication device of the called user agent 4 supporting(FIG. 2a ) and not supporting (FIG. 2b ) the ICE extension, a multimediaconnection comprising audio and video data is set up by executing theinventive method of sending an offer message comprising an extension tothe ICE protocol according to RFC 4245 to specify the IP transportaddress whereon the multiple media types can be multiplexed, wherein theoffer message comprising the extension indicates support for both themultiplexing and a non-multiplexing of the multiple media types, to thedestination communication device, the method is downward compatible withdestination communication device both supporting and not supporting theICE extension.

By executing the inventive method/source communication device mediatypes are enabled to he negotiated in one (SDP-)offer/answer cycle forboth the case when the destination communication device is capable ofhandling the multiplexing/bundling of the media types and the case whendestination communication device is a legacy device not aware of thiscapability.

The advantages are:

1. The initial (SDP-)Offer is able to describe both the multiplexed andnon-multiplexed cases in a way that is compatible with legacydestination communication device/implementations.

2. Only one offer/answer cycle is needed to negotiate both themultiplexed and non-multiplexed cases.

3. The inventive method/source communication device works for the itIPv4/IPv6 dual stack scenario in which the port eventually used may onlyinitially be signalled in the candidate line.

The invention may be executed with another form of offer message thanthe SDP offer described herein before as an embodiment. In FIG. 1, 2 a,2 b, the server 3 and/or the gateway 3 may be missing. Instead of audioand video data, other forms of data such as text may be combined withaudio and/or video data to form multimedia date to be multiplexed.

A technical feature or several technical features which has/have beendisclosed with respect to a single or several embodiments discussedherein before may be present also in another embodiment except itis/they are specified not to be present or it is impossible for it/themto be present for technical reasons.

1-16. (canceled)
 17. A communication apparatus comprising: a firstcommunication device comprising a processor and non-transitory computerreadable medium; the first communication device configured to generatean offer message identifying a first transport candidate forcommunication of a first type of data and a second transport candidatefor communication of the first type of data and a first transportcandidate for communication of a second type of data and a secondtransport candidate for communication of the second type of data, thefirst and second transport candidates for communication of the firsttype of data and the first and second transport candidates forcommunication of the second type of data supporting both multiplexingtransmission and non-multiplexing transmission; wherein the offermessage also comprises a first bundleport identifier indicating atransport address for multiplexing of the first type of data and asecond bundleport identifier indicating a single transport address formultiplexing of both the first type of data and the second type of data;the first communication device configured to send the offer message to asecond communication device to establish a communication connectionalong at least one payload path for the transmission of the first typeof data and the second type of data between the first and secondcommunication devices; and wherein the first communication device isconfigured to send the offer message prior to the first communicationdevice receiving information of a capability of the second communicationdevice to multiplex multiple media types on a transport address.
 18. Thecommunication apparatus of claim 17, comprising the second communicationdevice.
 19. The communication apparatus of claim 18, wherein the secondcommunication device comprises a processor and a non-transitory computerreadable medium.
 20. The communication apparatus of claim 18, whereinthe second communication device is a telephone, a mobile phone, apersonal digital assistant, a tablet, a laptop, or a computer.
 21. Thecommunication apparatus of claim 17, wherein the first type of data isaudio data and the second type of data is video data.
 22. Thecommunication apparatus of claim 17, wherein the first communicationdevice is a telephone, a mobile phone, a personal digital assistant, atablet, a laptop, or a computer.
 23. A method for negotiation of mediabetween a first communication device and a second communication device,the method comprising: the first communication device generating anoffer message identifying a first transport candidate for communicationof a first type of data and a second transport candidate forcommunication of the first type of data and a first transport candidatefor communication of a second type of data and a second transportcandidate for communication of the second type of data, the first andsecond transport candidates for communication of the first type of dataand the first and second transport candidates for communication of thesecond type of data supporting both multiplexing transmission andnon-multiplexing transmission, wherein the offer message also comprisesa first bundleport identifier indicating a transport address formultiplexing of the first type of data and a second bundleportidentifier indicating a single transport address for multiplexing ofboth the first type of data and the second type of data; the firstcommunication device sending the offer message to a second communicationdevice to establish a communication connection along at least onepayload path for the transmission of the first type of data and thesecond type of data between the first and second communication devices,the offer message being sent prior to the first communication devicereceiving information of a capability of the second communication deviceto multiplex multiple media types on a transport address; establishingonly a single payload path between the first and second communicationdevices for transmission of both the first type of data and the secondtype of data via multiplexing in response to an answer messageindicating that the second communication device supports multiplexing;establishing a first payload path between the first and secondcommunication devices for transmission of the first type of data and asecond payload path between the first and second communication devicesfor transmission of the second type of data in response to the answermessage indicating the second communication device does not supportmultiplexing.
 24. The method of claim 23, wherein the offer message hasan extension that is in accordance with Interactive ConnectivityEstablishment (ICE) protocol, the extension identifying transportaddresses for the first and second transport candidates forcommunication of the first type of data to identify the first and secondtransport candidates for communication of the first type of data andidentifying transport addresses for the first and second transportcandidates for communication of the second type of data to identify thefirst and second transport candidates for communication of the secondtype of data.
 25. The method of claim 23, wherein the transportaddresses are internet protocol (IP) transport addresses.
 26. The methodof claim 23, wherein the offer message is generated in accordance withSession Description Protocol (SDP).
 27. The method of claim 23,comprising: the first communication device receiving the answer messagefrom the second communication device.
 28. The method of claim 27,wherein the answer message is in accordance with Session DescriptionProtocol (SDP).
 29. The method of claim 23, wherein the single payloadpath is a 5 Tuple connection.
 30. The method of claim 23, wherein thesingle payload path has a single Internet Protocol (IP) transportaddress and a single IP port.
 31. The method of claim 23, wherein thefirst communication device is a telephone, a mobile phone, a personaldigital assistant, a tablet, a laptop, or a computer.
 32. The method ofclaim 23, also comprising: the second communication device responding tothe offer message by sending the answer message; the first communicationdevice receiving the answer message from the second communicationdevice.
 33. The method of claim 32, wherein the single payload pathbetween the first and second communication devices is a 5 Tupleconnection between the first and second communication devices.
 34. Themethod of claim 32, wherein the answer message is sent by the secondcommunication device independently of whether the second communicationdevice supports multiplexing of multiple media types.
 35. The method ofclaim 23, wherein the at least one payload path is established such thatonly a single offer/answer cycle between the first and secondcommunication devices takes place.
 36. A non-transitory machine readablemedium containing at least one program that is executable by a firstcommunication device, the first communication device performing a methoddefined by the at least one program when the at least one program isexecuted by the first communication device, the method comprising: thefirst communication device generating an offer message identifying afirst transport candidate for communication of a first type of data anda second transport candidate for communication of the first type of dataand a first transport candidate for communication of a second type ofdata and a second transport candidate for communication of the secondtype of data, the first and second transport candidates forcommunication of the first type of data and the first and secondtransport candidates for communication of the second type of datasupporting both multiplexing transmission and non-multiplexingtransmission, wherein the offer message also comprises a firstbundleport identifier indicating a transport address for multiplexing ofthe first type of data and a second bundleport identifier indicating asingle transport address for multiplexing of both the first type of dataand the second type of data; the first communication device sending theoffer message to a second communication device to establish acommunication connection along at least one payload path for thetransmission of the first type of data and the second type of databetween the first and second communication devices, the offer messagebeing sent prior to the first communication device receiving informationof a capability of the second communication device to multiplex multiplemedia types on a transport address.